End-to-End Content Delivery Network Incorporating Independently Operated Transparent Caches and Proxy Caches

ABSTRACT

Some embodiments provide an end-to-end federated CDN solution that assimilates a transparent caching server that is operated by a transparent caching server operator into a CDN that independently operates CDN caching servers. Specifically, the logs from the transparent caching server are assimilated into the CDN by aggregating the logs from the transparent caching server and processing the transparent caching server logs to identify network usage for content of a CDN content provider customer that is delivered by the transparent caching server. The network usage is then combined with the network usage that tracked by the CDN caching servers in order to provide comprehensive report metrics for the content provider customer and to bill the content provider customer for all network usage related to delivering the content provider customer&#39;s content irrespective of whether the content was delivered by a transparent caching server or a CDN caching server.

CLAIM OF BENEFIT TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. nonprovisionalapplication Ser. No. 13/401,721, entitled “End-to-End Content DeliveryNetwork Incorporating Independently Operated Transparent Caches andProxy Caches”, filed Feb. 21, 2012 which claims the benefit of U.S.provisional application 61/524,294, entitled “Open Content DeliveryNetwork Platform with Capacity Exchange”, filed Aug. 16, 2011. Thecontents of application Ser. Nos. 13/401,721 and 61/524,294 are herebyincorporated by reference.

TECHNICAL FIELD

The present invention relates to content caching and content deliverynetworks.

BACKGROUND ART

Content delivery networks (CDNs) have greatly improved the transfer ofcontent across data networks such as the Internet. One way that a CDNimproves the transfer of content is to reduce the distance that contenttravels in order to reach a destination. To do so, the CDN operatorstrategically locates surrogate origin servers, also referred to as CDNcaching servers or edge servers, at various points-of-presence (PoPs)that are geographically proximate to large numbers of end users. CDNcustomers are content providers that offload their content to the CDNcaching servers. The CDN caching servers cache the offloaded content anddeliver the content on behalf of the CDN customers or content providers.More particularly, from the geographically proximate locations of theCDN caching servers to the end users, the CDN caching servers serve thecached content to end users in a manner that is more efficient than ifthe content providers were to serve the content themselves. The CDN usesa traffic management system to route requests for the cached content tothe CDN caching server that can optimally deliver the requested contentto the requesting end user. As used hereafter, optimal delivery ofcontent refers to the most efficient available means by which contentcan be delivered from a server to an end user machine over a datanetwork. Optimal delivery of content may be quantified in terms oflatency, jitter, packet loss, distance, and overall end user experience.

Determination of the optimal CDN caching server may be based ongeographic proximity to the requesting end user as well as other factorssuch as load, capacity, and responsiveness of the CDN caching servers.The optimal CDN caching server delivers the requested content to therequesting end user in a manner that is more efficient than when originservers of the content provider (CDN customer) deliver the requestedcontent or when other CDN caching servers at different PoPs of the CDNdeliver the content. For example, a CDN operator may deploy CDN cachingservers to form PoPs in Los Angeles, Dallas, and New York. These cachingservers may cache content that is published by a particular contentprovider customer who has an origin server in Miami. When a requestingend user in San Francisco submits a request for the content of theparticular content provider customer, the CDN will deliver the contentfrom a CDN caching server at the Los Angeles PoP on behalf of theparticular content provider customer, as opposed to the much greaterdistance that would be required when delivering the content from theparticular content provider customer's origin server in Miami. In thismanner, the CDN reduces the latency, jitter, and amount of bufferingthat is experienced by the requesting end user.

Another advantage of the CDN is that it allows content providercustomers to offload infrastructure costs, configuration management, andmaintenance to the CDN. The CDN operator deploys and manages theinfrastructure for the delivery network and the CDN operator allocatesas much resources as needed to a particular content provider customer ata given time, with the ability for the particular content providercustomer to rapidly scale resources as needed. Content providercustomers only pay the CDN operator for the resources (e.g., bandwidth)that are used to serve the content provider customer's content from anyof the CDN's PoPs to whichever end users request that content. Contentprovider customers can therefore devote more time to the creation ofcontent and less time to the creation of an infrastructure that deliversthe content to end users. As a result of these and other benefits, manyCDNs are in operation today. Edgecast, Akamai, Limelight, and CDNetworksare some examples of currently operating CDNs.

A problem confronting any CDN operator is the inability to provide atrue end-to-end content delivery solution. This is because the CDNoperator does not control all links in the delivery chain over whichcontent is delivered from one of its CDN caching servers to an end user.Specifically, the CDN operator does not have control over one or more ofthe final links in the delivery chain. This discontinuity in thedelivery chain is primarily a result of the Telcos that are positionedbetween the CDN and the end users. A Telco means and refers to awireless or mobile service provider, broadband service provider, or anyinternet service provider (ISP). Telcos may be regional or nationalservice providers and may include service providers such as AT&T®,Verizon® and Charter Communications®. A Telco provides one or more endusers connectivity to data networks, including the Internet. Suchconnectivity enables the communication between the CDN caching serversand the end users. The Telco fully controls the components and thenetwork that enable such connectivity. As a result, a CDN operator istypically unable to locate its caching servers inside the Telco network,when the Telco wishes to maintain full control of its network. End usersthat are customers of a particular Telco, pay the Telco for access tothe data network. Payment may be in the form of monthly subscriptionfees or pay-per-increment of bandwidth usage. This payment in turn paysfor the cost of connecting the Telco network to other data networks,thereby providing end users of the Telco access to the Internet.

A Telco interrupts the end-to-end delivery capability of the CDN when itdeploys one or more transparent caching servers or proxy servers withinthe Telco-controlled network. Typically, the Telco deploys such serversat gateway locations, whereby content passing between the Telco networkand an external data network flows at some point through the transparentcaching server or proxy server. The terms transparent caching serverwill be used hereafter to refer to the functionality of either atransparent caching server or a proxy server. As is known to one ofordinary skill in the art, a transparent caching server is functionallydifferent and is operated independent of the CDN caching servers. Atransparent caching server can be configured by the Telco to specifycertain content that the Telco wishes to designate as hot (i.e.,popular) content, whereas the CDN caching servers are configured tocache content based on rules configured by the CDN operator or rulesprovided by their content provider customers. In further contrast to theCDN caching servers, a transparent caching server monitors contentpassing between a source (e.g., the external data network) and adestination (e.g., end-user customers of the Telco). The monitoring isperformed to determine what content to cache. The monitoring is alsoperformed in order to intercept requests for content that thetransparent caching server has cached, wherein intercepting a requestprevents the request from reaching an intended recipient that ordinarilyserves the requested content (e.g., a content provider server or a CDNcaching server). Upon intercepting a request, the transparent cachingserver can serve the content requested in the request from cache back tothe requestor, without the request reaching the intended recipient andwithout the intended recipient being aware that the content wasrequested or was served by another (i.e., the transparent cachingserver). CDN caching servers typically perform no such monitoring andinterception. Instead, CDN caching servers typically respond to arequest when the request is routed to a particular CDN caching serverusually as a result of some redirection, wherein the redirection mayinclude DNS redirection, aliasing and URL rewriting as some examples.

By deploying one or more transparent caching servers within a Telconetwork, the Telco, in a sense, can create and operate its own local CDNindependent of the external CDNs operated, for example, by Edgecast orAkamai. This further accelerates the delivery of content to the Telco'send users as the Telco is often the final link in the delivery chain tothe end users. Telcos benefit from the deployment of transparent cachingservers because such servers reduce the amount of traffic outside theTelco network, thereby reducing bandwidth costs for the Telco. Stateddifferently, some of the end user requested content can be served fromthe local cache of the transparent caching server that is internal tothe Telco network instead of having to use external data networkbandwidth when serving the requested content from CDN caching servers,origin servers of a content provider, or other servers that are locatedin the data network that is external to the data network operated by theTelco.

This interruption in the end-to-end delivery capability of the CDNprevents requests for certain content from reaching the CDN and frombeing serviced by the CDN. As a result, the revenue stream of the CDN isimpacted as less content is served by the CDN on behalf of the CDN'scontent provider customers. Also, the metrics computed by the CDN formeasuring the demand for content provider customer content and formeasuring the performance in delivering such content are impacted.Specifically, the measurements are inaccurate because the CDN no longerdelivers all content on behalf of its content provider customers. Forexample, there may be a thousand distinct requests for a particularcontent provider customer's content that the CDN is to deliver on behalfof the particular content provider customer. However, it may be thatonly seven hundred of those requests are serviced by the CDN's cachingservers and the other three hundred requests are intercepted beforereaching the CDN's caching servers and are instead serviced bytransparent caching servers operated by one or more Telcos. In thisscenario, the CDN will report to the particular content providercustomer that its content was requested only seven hundred times, whenin actuality the content was requested one thousand times. In otherwords, the performance measurements and other metrics related to thedelivery of the particular content provider customer's content and thatare reported by the CDN to the particular content provider customer willonly take into account the content delivered in response to the sevenhundred requests serviced by the CDN while omitting performancemeasurements and other metrics related to the three hundred requeststhat were intercepted and serviced by the transparent caching servers.As a result, the CDN underreports the demand for the particular contentprovider customer's content and any other metrics are inaccurate.

The interruption in the CDN's end-to-end delivery capability also raisesintellectual property rights issues. Based on the contract that thecontent provider customer establishes with the CDN, it may be that onlythe CDN is authorized to cache, host, distribute, or otherwise servecontent of the content provider customer and any transparent caching ofthe content provider customer's content violates the terms governing whois authorized to cache, host, distribute, or otherwise serve suchcontent.

Accordingly, there is a need for a true end-to-end CDN solution. Thereis a need for such an end-to-end CDN solution to leverage and accountfor components in the delivery chain that are both operated by the CDNand not operated by the CDN (i.e., operated by a third party such as aTelco). There is a need for such an end-to-end CDN solution to moreaccurately determine metrics associated with delivering content providercustomer content, to ensure authorized distribution of such content andto compensate the CDN for delivering all of such content.

SUMMARY OF THE INVENTION

It is an objective of the embodiments described herein to provide anend-to-end Content Delivery Network (CDN) solution. To do so, it is anobjective to assimilate components and existing resources of one or morethird-party intermediaries with those of a CDN, in order to create afederated CDN that has access to each link in the delivery chain overwhich content is delivered from a server of the federated CDN to endusers.

To achieve these and other objectives, some embodiments provide anend-to-end federated CDN solution that assimilates existingindependently-operated components and resources of a third-partyintermediary with those of a CDN. More specifically, some embodimentsprovide systems and methods for assimilating one or more transparentcaching servers that are operated by one or more transparent cachingserver operators (e.g., Telcos) into a CDN, wherein the CDN operates aset of CDN caching servers independent of the transparent cachingservers that are operated by the transparent caching server operators.

The systems and methods for performing such assimilation establish arelationship that is mutually beneficial to the transparent cachingserver operators as well as the CDN operator. From this relationship, atransparent caching server operator receives compensation (typicallymonetary) from a CDN operator in return for providing the CDN operatoraccess to the logs of the transparent caching servers that are operatedby the transparent caching server operator. The CDN operator benefitsfrom the gained access to the transparent caching server logs becausesuch access allows the CDN operator (1) to more accurately andcomprehensively track and report metrics related to the delivery ofcontent for the CDN's content provider customers and (2) to monetize theend-to-end delivery for CDN content provider customer content includingthe ability to monetize on the CDN content provider customer contentthat is delivered by the transparent caching servers, whereas prior tosuch assimilation, the transparent caching servers could intercept andserve such content without the CDN's knowledge and without the CDNlogging such usage. The assimilation of the transparent caching serversalso improves the overall content delivery capabilities of the CDN asthe transparent caching servers can deliver content on behalf of theCDN's content provider customers to some end users with less latencythan the CDN caching servers; and the CDN operator can account for thedelivery performance of the transparent caching servers as a result ofhaving access to their logs, thereby improving the overall contentdelivery performance of the CDN. Furthermore, the assimilation of thetransparent caching into the CDN can be performed with little to nochange on the part of the transparent caching server operator and withlittle additional overhead to the CDN operator.

In some embodiments, the systems and methods for creating the federatedCDN in which transparent caching servers are assimilated with CDNcaching servers involve establishing a sharing relationship between thetransparent caching server operator and the CDN operator. The sharingrelationship sets the conditions upon which the transparent cachingserver operator provides the CDN operator access to the logs of thetransparent caching servers. The sharing relationship further sets thecompensation (e.g., fixed or variable) that the CDN operator provides tothe transparent caching server operator in return for the access andalso the access credentials with which the CDN operator can remotelyaccess the transparent caching servers in order to aggregate the logsfrom the transparent caching servers.

In some embodiments, the systems and methods for creating the federatedCDN involve configuring a log processing server (i.e., administrativeserver) of the CDN to periodically aggregate the one or more logs fromeach assimilated transparent caching server through a remote connection.Using the remote connection, the log processing server may periodicallypull the logs from the transparent caching servers that have beenassimilated into the CDN. Alternatively, the assimilated transparentcaching servers may periodically push the logs to the log processingserver using the remote connection.

The log processing server processes each log in conjunction with anassociation table. The association table includes entries for relatingnetwork usage that is entered into the aggregated logs. By using theassociation table, some or all of the network usage in the aggregatedlogs is related back to a CDN content provider customer who originatesor otherwise authorizes dissemination of the content by the CDN (i.e., acontent provider that has contracted the CDN to deliver content on itsbehalf).

In some embodiments, the network usage from the aggregated transparentcaching server logs that is identified for a CDN's content providercustomer is used to report on the delivery of the content providercustomer's content. From the identified network usage, the logprocessing server derives metrics that quantify performance, demand, andother parameters relating to the delivery of the content providercustomer's content. In some such embodiments, the network usageidentified from the transparent caching server logs is combined withnetwork usage for the same content provider customer as identified inlogs that are aggregated from the CDN caching servers. In so doing, theCDN derives comprehensive and accurate performance metrics that accountfor CDN-controlled components as well as components controlled by thirdparties, both of which are nevertheless used to deliver content of thecontent provider customer.

In some embodiments, the network usage from the aggregated transparentcaching server logs that is identified for a CDN's content providercustomer is used to bill the content provider customer for that networkusage. Specifically, the content provider customer is assessed a fee forthe network usage that is associated with the content that has beendelivered on behalf of the content provider customer by the transparentcaching server that is now assimilated into the CDN. This fee may becomputed using the same algorithms and criteria that would have beenused if the content was delivered from a caching server of the CDNinstead of the transparent caching server. In some embodiments, theassessed fee is a fee that is derived based on the network usage that isassociated with the content delivery identified in the logs aggregatedfrom the transparent caching servers and also the network usage that isidentified in the logs aggregated from caching servers of the CDN.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to achieve a better understanding of the nature of the presentinvention, preferred embodiments for the end-to-end CDN solution willnow be described, by way of example only, with reference to theaccompanying drawings in which:

FIG. 1 presents an exemplary framework for the end-to-end CDN solutionin accordance with some embodiments.

FIG. 2 presents a process for assimilating transparent caching serversinto a CDN in accordance with some embodiments.

FIG. 3 presents a process for utilizing assimilated transparent cachingserver logs to provide an end-to-end CDN solution in accordance withsome embodiments.

FIG. 4 illustrates processing transparent caching server logs inaccordance with some embodiments.

FIG. 5 conceptually illustrates generating comprehensive and detailedreports for the combined network usage of different content providercustomers of the CDN in accordance with some embodiments.

FIG. 6 illustrates the links in the delivery chain that contenttypically traverses when passing from a CDN to an end user.

FIG. 7 illustrates how a first CDN operator can further monetize atransparent caching server log by redistributing the transparent cachingserver log to second and third CDN operators in accordance with someembodiments.

FIG. 8 presents a process that is performed by an enhanced transparentcaching server to utilize the CDN keys in support of the end-to-end CDNsolution.

FIG. 9 illustrates assimilating a transparent caching server as anextended PoP of the CDN in accordance with some embodiments.

FIG. 10 presents a process performed by a broker acting as a reseller oftransparent caching server logs in accordance with some embodiments.

FIG. 11 illustrates a fully federated CDN wherein a first CDN operatorassimilates resources of a transparent caching server operator andresources of a second CDN operator in accordance with some embodiments.

FIG. 12 illustrates a computer system or server with which someembodiments are implemented.

DETAILED DESCRIPTION

In the following detailed description, numerous details, examples, andembodiments for systems and methods for the end-to-end Content DeliveryNetwork (CDN) solution are set forth and described. As one skilled inthe art would understand in light of the present description, thesesystems and methods are not limited to the embodiments set forth, andthese systems and methods may be practiced without some of the specificdetails and examples discussed. Also, reference is made to theaccompanying figures, which illustrate specific embodiments in which thesystems and methods can be practiced. It is to be understood that otherembodiments can be used and structural changes can be made withoutdeparting from the scope of the embodiments herein described.

I. Framework

FIG. 1 presents an exemplary framework for the end-to-end CDN solutionin accordance with some embodiments. The end-to-end CDN solution is theresult of assimilating two transparent caching servers 110 and 120 thatare independently operated by different Telcos 130 and 140 with CDNcaching servers 160 of a CDN 150. The end-to-end CDN solution, allowsthe CDN 150 to expand its reach by leveraging already deployed resourcesof the Telcos 130 and 140 (i.e., the transparent caching servers 110 and120). In so doing, the CDN 150 improves its content deliveryperformance, provides more comprehensive reporting, and lowers overallcost of content delivery.

Each transparent caching server 110 and 120 may be representative of afully integrated machine having the software and hardware necessary toperform transparent caching or proxy caching. Each transparent cachingserver 110 and 120 may alternatively be representative of a machine thatis integrated with the necessary software or hardware to performtransparent caching or proxy caching in conjunction with otherfunctionality. Furthermore, each transparent caching server 110 and 120may be representative of one or more physical machines or virtualmachines that run on one or more physical machines to performtransparent caching or proxy caching. Transparent caching and proxycaching is defined in conformance with the well understood industrydefinition. Accordingly, the terms are intended to generally include anymachine that performs a monitoring and/or intercepting function as partof a caching function.

The monitoring and caching function is illustrated by the transparentcaching server 110 while the intercepting and caching function isillustrated by the transparent caching server 120. The transparentcaching server 110 is positioned between the end user subscribers of theTelco 130 and a gateway from which the end user subscribers request andobtain content from an external data network such as the Internet. Thetransparent caching server 110 monitors content passing between a source(e.g., the external data network) and a destination (e.g., an end usersubscriber of the Telco 130). The monitoring is performed to analyze enduser subscriber submitted requests for content in order to determinewhether the transparent caching server 110 has the requested contentcached. In this example, the transparent caching server 110 receives arequest from an end user subscriber of Telco 130, analyzes the request,and determines that the requested content is not cached. In someembodiments, the transparent caching server 110 does not intercept therequest and allows the request to pass into the external data networkfor routing to the appropriate source. In some embodiments, thetransparent caching server 110 intercepts the request, but reissues therequest to the original intended recipient in the external data networkwith the transparent caching server 110 identified as the requestoriginator. As shown, the passed through or reissued request is routedto a CDN caching server of the CDN 150 that serves the content back. Theserved content passes through the transparent caching server 110. Thetransparent caching server 110 monitors the content and identifies thecontent being sent in response to the request and so the transparentcaching server 110 caches the content. In so doing, any subsequentrequests for the same content by an end user subscriber of the Telco 130can be intercepted and the content can be served from the transparentcaching server 110 instead of the more remote CDN caching server or moreremote content provider server that may also host the requested content.For the purposes of the discussion that is to follow, it is irrelevanthow the transparent caching server 110 performs transparent cachingwhether by passing through requests or intercepting and reissuingrequests. Accordingly, any method of operation that is well known in theart is adaptable and applicable to the end-to-end caching solutiondescribed herein.

Similar to the positioning of the transparent caching server 110, thetransparent caching server 120 is positioned between the end usersubscribers of the Telco 140 and the external data network (i.e.,Internet). The transparent caching server 120 monitors requests that areissued by the end user subscribers of the Telco 140. In the illustratedexample, the transparent caching server 120 identifies a request forcontent that the transparent caching server 120 has cached. Accordingly,the transparent caching server 120 intercepts the request therebypreventing the request from being forwarded to the external data networkand, in turn, preventing the request from being received by a CDNcaching server of the CDN 150 or content provider server that hosts therequested content. The transparent caching server 120 then satisfies theintercepted request by passing the requested content from its cache tothe requesting end user subscriber of Telco 140.

The transparent caching server 110 is independently operated by theTelco 130 and the transparent caching server 120 is independentlyoperated by the Telco 140 such that access to the transparent cachingserver is ordinarily restricted to the operating entity. Eachtransparent caching server 110 and 120 is assigned a network address(i.e., an Internet Protocol (IP) address) such that it may be accessedusing a remote connection. The remote connection may be establishedusing the HyperText Transfer Protocol (HTTP), File Transfer Protocol(FTP), Secure Shell (SSH) protocol, Spanning Tree Protocol (STP),Transmission Control Protocol (TCP), or other networking protocol. Theremote connection can be used to manage the transparent caching serverby configuring the rules for how the transparent caching serverdetermines what content to cache and when to cache the content. Theremote connection can also be used to retrieve and view the logs of thetransparent caching servers 110 and 120. The log for the transparentcaching server 110 tracks the content that was delivered by thetransparent caching server 110. The parameters tracked to the logtypically include at least one identifier for identifying the contentthat was delivered and bandwidth utilization that is associated withdelivering the content. The identifier for identifying the content mayinclude an IP address, Uniform Resource Identifier (URI), or stringrepresenting the content name. The bandwidth utilization may bequantified by a file size or kilobyte/megabyte per second with anassociated amount of time needed to deliver the content. It should beapparent to one of ordinary skill in the art that the log may includeadditional or other parameters for identifying the content that isdelivered by the transparent caching server and for identifying thesource entity and/or destination entity for the delivered content.

As noted above, the Telcos 130 and 140 are service providers thatprovide one or more end user subscribers connectivity to data networks,including the Internet. The Telcos 130 and 140 are the initial point ofentry for the end users to these data networks. Also, the Telcos 130 and140 are the final link in the delivery chain (or path) for content thatis delivered from the data networks to the end user subscribers. Forpurposes of simplicity, the other components besides the transparentcaching servers of the Telcos 130 and 140 are abstracted and not shown.Though Telcos 130 and 140 are presented in FIG. 1, it should be apparentto one of ordinary skill in the art that the Telcos 130 and 140 may besubstituted by any operator of one or more transparent caching serversthat operates the transparent caching servers independent of the CDN 150and also locates the transparent caching servers at some point along thedelivery path in which content is passed from the CDN 150 or from anyexternal data network to one or more end users. Therefore, it should beapparent to one of ordinary skill in the art that the operation of thetransparent caching servers 110 and 120 need not be confined to theillustrated Telcos (130 and 140), but that the transparent cachingservers 110 and 120 can operate at any intermediary location between asource and a destination irrespective of whether the intermediarylocation is at a location in a Telco or some other network or serviceprovider (e.g., any ISP).

Some appliance manufacturers for the transparent caching servers 110 and120, and more generally, for the transparent caching servers envisionedfor the federated end-to-end CDN solution are those manufactured byPeerApp Ltd. and Blue Coat Systems Inc. It is irrelevant whether thetransparent caching servers that are assimilated to create theend-to-end solution and that are shown in the exemplary framework ofFIG. 1 are identical or different machines from the same manufacturer ordifferent manufacturers.

The CDN 150 is conceptually illustrated with a distributed set of CDNcaching servers 160, traffic management servers 170, and a logprocessing server 180. The figure also illustrates the interactions thatCDN customers, including content provider customers, have with the CDN150 and interactions that content consumers or end users have with theCDN 150.

Each CDN caching server of the set of CDN caching servers 160 mayrepresent a single physical machine or a cluster of machines that servescontent on behalf of different CDN content provider customers to endusers of the illustrated Telcos 130 and 140 and to any other contentconsumer that requests content that the CDN 150 has been contracted toserve on behalf of the CDN content provider customers. One set of CDNcaching servers 160 may represent a server farm for a geographicallyproximate set of physically separate machines or a set of virtualmachines that execute over partitioned sets of resources of one or morephysically separate machines. The set of CDN caching servers 160 aredistributed across different edge regions of a data network (i.e., theInternet) to facilitate accelerated delivery of content. Specifically,the set of CDN caching servers 160 are distributed to form differentpoints-of-presence (PoPs) at these different edge regions.

The CDN 150 uses the traffic management servers 170 to route an end userthat requests content of a content provider customer to the closest PoPin order to optimally serve the requested content to the requesting enduser. Stated differently, the traffic management servers 170 resolverequests for content that is hosted by the CDN 150 to the CDN cachingserver that optimally serves that content back to the end user, whereinoptimally serving the content is quantified in terms of proximity,latency, jitter, packet loss, time to buffer, and other such measureablemetrics. Different CDN implementations use different traffic managementschemes to achieve such routing to the optimal PoPs or CDN cachingservers. As one example, the traffic management servers 170 performAnycast routing to identify a CDN caching server from the set of CDNcaching servers 160 that can optimally serve requested content to aparticular end user requesting the content. It should be apparent thatthe traffic management servers 170 can include different combinations ofDomain Name System (DNS) servers, load balancers, and routers performingAnycast or Border Gateway Protocol (BGP) routing.

The log processing server 180 may include a central server of the CDN150 or a distributed set of interoperating servers that perform theconfiguration control, reporting, and billing functionality for the CDN150. Content providers register with the CDN 150 in order to accessservices and functionality of the CDN 150. Accordingly, contentproviders are also referred to as customers of the CDN 150. Onceregistered, CDN content provider customers can interface with the logprocessing server 180 to specify a configuration, upload content, andview performance reports. The log processing server 180 also aggregatesstatistical and performance data from each server of the set of CDNcaching servers 160. The log processing server 180 processes theaggregated data to produce usage and performance reports. From thesereports, CDN content provider customers can better understand the demandfor their content, the performance provided by the CDN 150 in deliveringtheir content, and the need for capacity reallocation, among other uses.The log processing server 180 also processes the aggregated logs to billthe CDN's content provider customers for the network usage that isrelated to the delivery of the content provider customers' content bythe CDN caching servers 160. Network usage generally refers to an amountof bandwidth consumed when delivering content from a source to adestination. Network usage may be quantified as a bits/bytes consumedover some duration (e.g., 10 KB/s for 10 seconds) or as the file sizefor content that is delivered from a source to a destination.

By assimilating the transparent caching servers 110 and 120 with thecaching servers 160 of the CDN 150, the CDN 150 is able to expand itsreach by leveraging already deployed resources of third parties. In sodoing, the overall content delivery performance of the CDN 150 isimproved. This is a result of the closer geographic proximity that thetransparent caching servers 110 and 120 have to the end user subscribersof the Telcos 130 and 140 relative to the CDN caching servers 160 andbecause the CDN 150 can factor, as a result of the assimilation, thecontent delivery performance of the transparent caching servers 110 and120 with the content delivery performance of its own CDN caching servers160 when determining overall content delivery performance for the CDNcontent provider customers. Prior to the end-to-end CDN solution and theassimilation of the transparent caching servers 110 and 120 into the CDN150, the content delivery performance of the transparent caching servers110 and 120 would be unaccounted for by the CDN 150 when the CDN 150reported content delivery performance to its content provider customersand when some content of those content provider customers was actuallybeing served by the transparent caching servers 110 and 120. However,the end-to-end solution resolves these issues and enables the CDN 150 toproduce comprehensive and accurate reporting that not only accounts forthe content delivery performance of the CDN caching servers 160, butthat also accounts for the content delivery performance of thetransparent caching servers 110 and 120 that are located at the finallink in the delivery chain between end users and the CDN 150. Also,assimilating the transparent caching servers 110 and 120 grows the CDN150 footprint and the content delivery capabilities of the CDN 150. Inso doing, the overall cost for content delivery is lowered.Specifically, the traditional CDN model has each CDN compete with otherCDNs, Telcos, etc. In competing with one another, CDNs are in acontinual struggle to expand their capacity and capabilities. Thisexpansion results in each CDN incurring the same or similarinfrastructure costs related to the deployment of caching servers todesignated high traffic areas. This further results in redundantdeployment of resources, whereby multiple CDNs operate in the sameregions with excess capacity as a result of cannibalizing contentdelivery from one another. The cost for this redundant deployment ofresources is incurred by the CDNs. The CDNs propagate this cost to theircontent provider customers in the form of higher fees being charged forthe bandwidth that is consumed for delivering the content of the contentprovider customers. The content provider customers then propagate theincreased cost to the end users that consume the content in the form ofhigher subscription fees, content access fees, or other fees.

II. End-to-End Cdn Solution

FIGS. 2 and 3 present processes for implementing the end-to-end CDNsolution through the assimilation of transparent caching servers with aCDN in accordance with some embodiments. FIG. 2 presents a process 200for assimilating transparent caching servers into a CDN in accordancewith some embodiments. This process 200 describes a reciprocal bilateralagreement between two independent parties. The first party to thebilateral agreement is a transparent caching server operator thatoperates a transparent caching server independent of the second party.The transparent caching server operator can include a Telco, ISP, or anyother entity that operates one or more transparent caching servers. Thesecond party to the bilateral agreement is a CDN operator that operatesa CDN and a distributed set of CDN caching servers. EdgeCast, Akamai andLimeLight are examples of different CDN operators.

As part of the bilateral agreement, the CDN operator receives (at 210)access to the logs of the transparent caching servers that are operatedby the transparent caching server operator. In return, the CDN operatorcompensates (at 220) the transparent caching server operator for suchlog access. The terms and conditions for the bilateral agreement arememorialized to detail the bilateral agreement between the transparentcaching server operator and the CDN operator. The CDN operator can thenassimilate (at 230) the transparent caching servers of the transparentcaching server operator into its CDN in the manner described withreference to FIG. 3 below.

The reciprocal bilateral agreement entered into between the transparentcaching server operator and the CDN operator is one that can beexclusive in nature or one that is non-exclusive in nature. An exclusivebilateral agreement is one in which only the CDN operator (that is aparty to the agreement) receives or is provided any form of access tothe logs of the transparent caching servers. Stated differently, thetransparent caching server operator is contractually prevented fromdistributing or otherwise providing other CDN operators or otherentities that are not a party to the bilateral agreement access to thetransparent caching server logs. A non-exclusive bilateral agreement isone that does not contractually restrict the transparent caching serveroperator from providing other entities access to the logs of thetransparent caching servers. The bilateral agreement and, by extension,the process 200 may be initiated by either the CDN operator or thetransparent caching server operator.

The CDN operator may receive the logs of the transparent caching serversvia different pull or push mechanisms. For some such push or pullmechanisms, the transparent caching server operator provides the CDNoperator with remote access to the transparent caching servers.Typically, a transparent caching server has a network interface withwhich the transparent caching server can be remotely accessed using anetwork communication protocol. In some embodiments, the remote accessto a transparent caching server is established using HTTP, FTP, SSH,STP, or some other network protocol. This remote access may berestricted to authorized users. In some embodiments, the transparentcaching server operator configures the transparent caching servers withusername and password combinations that can be used to identify theauthorized users. Therefore as part of the bilateral agreement enteredin between the CDN operator and the transparent caching server operator,the transparent caching server operator may provide the CDN operatorwith the secure access credentials (e.g., username and password) thatthe CDN operator can use to remotely access the transparent cachingservers in order to obtain the logs from those servers. In someembodiments, the transparent caching servers are configured by thetransparent caching server operator to periodically push the logs to theCDN operator. In some embodiments, the transparent caching serveroperator may also provide the CDN operator access to the logs withoutproviding the CDN operator remote access to the transparent cachingservers. For instance, as part of the bilateral agreement, thetransparent caching server operator agrees to periodically (e.g., weeklyor monthly) aggregate the logs from its transparent caching servers andthen pass the aggregated logs to the CDN operator, such that thetransparent caching server operator maintains full control over itstransparent caching servers. This latter method of providing transparentcaching server logs may be preferred when the transparent caching serveroperator provides the CDN operator only partial access to the logs. Forexample, the transparent caching server operator may not want the CDNoperator to know all the content that is being served from itstransparent caching servers. Therefore, the transparent caching serveroperator can filter the logs before providing the CDN operator access tothe logs. The filtering can be performed to remove usage entries thatidentify content that is originated or sourced by a content providerthat is not a customer of the CDN. The CDN operator may provide thetransparent caching server operator identifiers for identifying thecontent providers that are the CDN's customers and whose usage shouldnot be filtered from the transparent caching server logs when filteringis to be performed.

As noted above, the CDN operator compensates (at 220) the transparentcaching server operator for the transparent caching server log access.In some embodiments, the CDN operator provides fixed compensation to thetransparent caching server operator for access to each transparentcaching server log. The compensation may be monetary. For example, theCDN pays the transparent caching server operator ten dollars for eachlog that the CDN gains access to. The compensation may also berecurring, such that the CDN operator pays the transparent cachingserver operator ten dollars every month for monthly access to the logsof a particular transparent caching server. The compensation may also bean exchange of services. For instance, the transparent caching serveroperator provides the CDN operator free access to the transparentcaching server logs when the CDN operator agrees to deliver content onbehalf of the transparent caching server operator to end users that areoutside the network controlled by the transparent caching serveroperator. It should be apparent to one of ordinary skill in the art thatthe compensation may be provided with other means in which some economicvalue is imparted to the transparent caching server operator forproviding the CDN operator access to the transparent caching serverlogs. In some embodiments, the CDN operator provides variablecompensation to the transparent caching server operator. The variablecompensation may be based on a specified set of conditions. As aspecific example, the variable compensation may be based on a percentageof monetization that the CDN operator realizes from the log. Continuingwith the example, if the log identifies usage for the CDN's contentprovider customers and the CDN operator is able to charge the contentprovider customers one hundred dollars for such usage, the variablecompensation may be ten percent of the fee collected by the CDN, which,in this example, amounts to ten dollars of compensation that the CDNoperator provides back to the transparent caching server operator.

Accordingly, the bilateral agreement is a reciprocal agreement in whichthe CDN operator gains access to the logs of the transparent cachingservers and the transparent caching server operator is compensated bythe CDN operator for such access. This reciprocity provides incentive toboth parties to enter into the bilateral agreement, as the bilateralagreement is one that both the transparent caching server operator andthe CDN operator benefit from. Specifically, the CDN operator gainsaccess to the logs of the transparent caching servers. These logs enablethe CDN to more comprehensively track network usage for the CDN'scontent provider customers. Before assimilation of the transparentcaching servers, the CDN operator could only reliably track networkusage to the level of the Telco or to the level of where a transparentcaching server existed in the delivery chain in which content is passedfrom a CDN caching server to an end user. After assimilation of thetransparent caching servers, the CDN operator can reliably trackend-to-end network usage all the way down to the end user level. Thisallows the CDN operator to produce more comprehensive and detailedreports, performance measurements, and other metrics relating to thedelivery of the CDN's content provider customers' content to the endusers. Also, by gaining access to each link in the delivery chain to theend user, the CDN operator is able to accurately bill its contentprovider customers for network usage relating to delivering the contentprovider customers' content to each end user. Before such assimilation,it was likely that a transparent caching server at an intermediaryposition in the delivery chain would cache content the first time it ispassed from a CDN caching server to a requesting end user. Then, asubsequent request for the same content by an end user at the end of thesame delivery chain would not reach the CDN and would instead beintercepted and served from the transparent caching server cache withoutthe CDN's knowledge. As a result, content provider customers had theircontent partially delivered free of charge. After assimilation of thetransparent caching servers into the CDN, the content provider customersare billed for all network usage that is related to delivering theircontent to end users, even if such delivery is accelerated by one ormore transparent caching servers. The transparent caching serveroperator also benefits from this reciprocal bilateral agreement becausethe transparent caching server operator would previously receive nocompensation for delivering the CDN's content provider customers'content, even though bandwidth was consumed when delivering such contentfrom the transparent caching server's cache to the end users. Byentering into the reciprocal bilateral agreement with the CDN operator,the CDN operator indirectly compensates the transparent caching serveroperator for such network usage by directly compensating the transparentcaching server operator for access to the logs that are then used topass the network usage fees to the CDN's appropriate content providercustomer.

FIG. 3 presents a process 300 for utilizing assimilated transparentcaching server logs to provide an end-to-end CDN solution in accordancewith some embodiments. The process 300 commences once a bilateralagreement has been formalized with one or more transparent cachingserver operators. The process 300 is performed by a CDN operator. Morespecifically, the process 300 is a machine-implemented process that isperformed by a particular machine under control of the CDN operator. Insome embodiments, the process 300 is performed by any server of the CDNoperator that is responsible for billing in the CDN, such as the logprocessing server described with reference to FIG. 1 above. Themachine-implemented process is embodied as a set of instructions for aprogram that is stored to a non-transitory computer-readable storagemedium and the program is executed by a microprocessor to automatedlyperform the instructions recited below.

The process 300 begins by aggregating (at 310) logs from the transparentcaching servers to which the CDN operator has been provided access,pursuant to one or more bilateral agreements. The logs may be aggregatedfrom transparent caching servers that are operated by differentoperators (e.g., a first transparent caching server that is operated bya first Telco and a second transparent caching server that is operatedby a second Telco). As noted above, the logs may be aggregated by (1)remotely accessing the transparent caching servers and pulling the logsfrom the remotely accessed servers, (2) configuring the transparentcaching servers to periodically push the logs to the CDN operator, or(3) obtaining the logs from the transparent caching server operator.Accordingly, aggregation may involve downloading the logs from theservers, retrieving copies of the logs from the servers, or having thelogs pushed from the servers via a file transfer mechanism such as FTP.

The process also aggregates (at 315) logs from CDN caching servers thatare operated by the CDN operator. In embodiments involving a federatedCDN, the process may aggregate logs from CDN caching servers that areoperated by a first CDN operator and logs from CDN caching servers thatare operated by a second CDN operator, wherein the first and second CDNoperators participate in the federated CDN. The CDN log processingserver may aggregate the CDN caching server logs using a pull mechanism,whereby the log processing server remotely accesses each of the CDNcaching servers and downloads the logs from the CDN caching servers.Alternatively, the CDN caching servers may periodically push their logsto the log processing server.

The process processes (at 320) the aggregated logs of the transparentcaching servers. The processing is performed to identify network usagethat is related to the delivery of content for content providers thatare customers of the CDN. In some embodiments, the processing performedat step 320 involves filtering the aggregated logs to remove networkusage that is related to delivering content for content providers thatare not customers of the CDN operator. In some embodiments, theprocessing performed at step 320 involves filtering the network usagethat is related to delivering content for content providers that arecustomers of the CDN operator and storing the filtered usage to adifferent filtered log. In some embodiments, the processing performed atstep 320 involves processing the aggregated logs in conjunction with anassociation table. The association table aids in identifying networkusage in the logs that is related to delivering content for differentcontent providers that are customers of the CDN operator. In someembodiments, the association table contains a list of identifiers thatidentify the CDN's content provider customers based on IP addresses,URIs, DNS records (e.g., CNAMEs), etc. The CDN operator is providedthese identifiers when a content provider registers as a customer of theCDN operator in order to have the CDN operator serve the contentprovider customer's content on behalf of the content provider customer.At that time, the CDN can enter the identifiers to the associationtable.

FIG. 4 illustrates processing transparent caching server logs toidentify network usage that is related to the delivery of content forcontent providers that are customers of the CDN in accordance with someembodiments. As with the process 300 of FIG. 3 above, the processingillustrated in FIG. 4 may be performed by a log processing server of theCDN. The figure illustrates log 410 that is aggregated from atransparent caching server, an association table 420 used by the logprocessing server in processing the log 410, and the log after it hasbeen processed 430 (i.e., the post-processed log 430).

The transparent caching server log 410 tracks various network usagemetrics related to content that is delivered from the transparentcaching server that produced the log. Though simplified for explanatorypurposes, the log 410 records one or more addressing identifiers 440,content identifiers 450, and network usage identifiers 460 for each itemof content that is delivered by the transparent caching server.Different transparent caching servers record different identifiers,parameters, or metrics in the logs. Also, the logs aggregated fromdifferent transparent caching servers may present the recordedidentifiers, parameters, or metrics in different formats. In someembodiments, the log processing server performs a pre-processing routineon the aggregated transparent caching server log to remove extraneousidentifiers, parameters, or metrics and to format the remainingidentifiers, parameters, or metrics according to a common format thatincludes some common baseline set of identifiers, parameters, ormetrics.

In some embodiments, the addressing identifiers 440 identify the sourceand/or destination associated with the delivered content. The source anddestination are typically addressed with different Internet Protocol(IP) addresses, although it should be apparent to one of ordinary skillthat any addressing scheme may be used to identify the source anddestination. The source addressing identifier identifies the source fromwhich the delivered content is originally requested. Because atransparent caching server intercepts requests before they reach thecontent source, the source will typically identify a content providerthat originates or is the source for the content being delivered.However, DNS resolution may cause the source addressing identifier toinstead identify an address for a CDN caching server that deliverscontent on behalf of a particular content provider customer. Thedestination addressing identifier identifies the end user who requestedand received the delivered content. The addressing identifiers 440 canbe extracted from the header of the content request that is interceptedby the transparent caching server. For instance, the addressingidentifiers 440 may include a source IP address and a destination IPaddress that are extracted from the header of an IP packet thatencapsulates the content request. Alternatively, the domain namespecified in the header of an HTTP GET request packet can be used toidentify the source for the requested content. The extracted addressingidentifiers 440 can then be entered in the log in association with thenetwork usage that is required to deliver the requested content from thetransparent caching server to the requesting end user.

The content identifiers 450 identify the delivered content. In someembodiments, the content identifiers 450 include the Uniform ResourceIdentifier (URI) that is used to request the content. Alternatively, thecontent identifiers 450 may include an object or file name. The contentidentifiers 450 are typically extracted from the header of the contentrequest that was intercepted by the transparent caching server. Forinstance, the URI can be extracted from the header of an HTTP GETrequest packet. The extracted content identifiers 450 may be enteredinto the transparent caching server log in association with addressingidentifiers 440 and the network usage that is required to deliver thecontent identified in the URI from the transparent caching server to therequesting end user.

The network usage identifiers 460 identify the network usage related todelivering the content from the transparent caching server to therequesting end user. Network usage is generally quantified as an amountof bandwidth that is consumed to serve the requested content from thetransparent caching server to the requesting end user. The bandwidth maybe represented as a file size for the content that is delivered from thetransparent caching server to the requesting end user. Alternatively,the bandwidth may be represented as a duration and an average amount ofbandwidth used over the duration (e.g., 10 Kbps for 10 seconds). Itshould be apparent to one of ordinary skill in the art that the networkusage identifiers 460 may include any identifiers that quantify a rateor amount of data transfer from the transparent caching server to therequesting end user.

The association table 420 includes a list of identifiers for identifyingthe content provider customers of the CDN operator. In some embodiments,the list of identifiers includes IP addresses for the origin servers ofthe content provider customers, wherein an origin server is a serverthat is operated by a content provider customer and that hosts contentof the content provider customer. In some embodiments, the list ofidentifiers includes URIs, object names, or file names identifying thecontent for the CDN's content provider customers. As was noted above,this information is acquired by the CDN operator when the contentprovider customers register with the CDN operator to have their contentdelivered by the CDN operator.

The processing (at step 320) involves matching identifiers from the log410 to identifiers in the association table 420 in order to identifynetwork usage from the transparent caching server logs that relate todelivered content for the CDN's content provider customers. When one ormore identifiers from the association table 420 match to one or moreidentifiers associated with an entry in the transparent caching serverlog 410, that entry is entered to the post-processed log 430. In thismanner, the post-processed log 430 records network usage from thetransparent caching server log 410 that relates to the delivery ofcontent for the CDN's content provider customers. As shown, two entries470 and 480 from the log 410 identify network usage that is related tocontent that is delivered for the CDN's content provider customers.Specifically, the URI associated with entry 470 identifies a domain namefor a CDN content provider customer and the source IP address associatedwith entry 480 identifies an IP address for an origin server of a CDNcontent provider customer. The other entries from log 410 may be omittedfrom the post-processed log 430 or otherwise denoted in thepost-processed log 430 as not pertaining to the CDN's content providercustomers.

With reference back to FIG. 3, the post-processed transparent cachingserver log (e.g., log 430) is integrated (at 330) for report generation.In some embodiments, integrating (at 330) the post-processed transparentcaching server log for report generation involves identifying thenetwork usage for each content provider customer of the CDN that isrecorded to the post-processed transparent caching server logs and theaggregated CDN caching server logs and producing a comprehensive anddetailed report for the combined network usage.

FIG. 5 conceptually illustrates generating comprehensive and detailedreports for the combined network usage of different content providercustomers of the CDN in accordance with some embodiments. This figureillustrates post-processed transparent caching server log 510,post-processed transparent caching server log 520, CDN caching serverlog 530, and CDN caching server log 540. The figure also illustrates twocomprehensive reports 550 and 560 that are generated for two contentprovider customers of the CDN as a result of assimilating thepost-processed transparent caching server logs 510 and 520 andintegrating the network usage therein with the network usage identifiedin the CDN caching servers logs 530 and 540. The post-processed log 510may be aggregated from a transparent caching server that is operated bya first Telco and the post-processed log 520 may be aggregated from atransparent caching server that is operated by the first Telco or asecond Telco. The detailed reports 550 and 560 may be generated by a logprocessing server of the CDN.

To generate the report 550 for the first content provider customer ofthe CDN, the log processing server identifies the network usage in eachof the logs 510-540 that is related to delivering the first contentprovider customer's content. This identification can be made using anassociation table such as the one described above with reference to FIG.4, wherein various identifiers are provided to identify content andassociated network usage that belongs to the first content providercustomer and the second content provider customer of the CDN. Forinstance, the association table may include one or more IP addresses,URIs, DNS records that individually or in combination identify the firstcontent provider customer of the CDN. As shown, the log processingserver identifies entry 570 from log 510, entry 575 from log 520, andentry 580 from log 540 as entries that identify network usage that isrelated to the delivery of the first content provider customer'scontent. These entries 570-580 are then grouped to produce the report550. In producing the report 550, the log processing server may formatthe entries 570-580 such that the resulting report 550 is uniformlyformatted. In producing the report 550, the log processing server mayanalyze the entries 570-580 to identify trends or produce statisticaldata from the resulting aggregated set of data. For instance, theanalysis of the collective set of entries 570-580 can yield the totalnetwork usage for delivering a particular item of content of the firstcontent provider customer of the CDN to any number of end users or thetotal network usage that is associated with delivering all of the firstcontent provider customer's content. Assuming that each log 510-540tracks network usage over the same specified duration, entry 570identifies 10 megabytes (MB) of network usage for delivering firstcontent of the first content provider customer, entry 575 identifies 1MB of network usage for delivering second content of the first contentprovider customer, and entry 580 identifies 10 MB of network usage fordelivering the first content of the first content provider customer.Accordingly, the total network usage for delivering all content of thefirst content provider customer over the specified duration is 21 MB andthe total network usage for delivering the first content of the firstcontent provider customer is 20 MB.

To generate the report 560, the log processing server identifies entry585 from transparent caching server log 520 and entry 590 from CDNcaching server log 530 as entries that identify network usage that isrelated to the delivery of the second content provider customer'scontent. As above, these entries 585-590 are grouped to produce thereport 560 wherein producing the report 560 may include formattingand/or analyzing the entries 585-590.

The reports 550 and 560 may be viewable through a graphical orinteractive interface provided by the CDN. The reports 550 and 560 mayalso be sent to the customers on a periodic basis via email, traditionalmail, or some other delivery means. In some embodiments, the reports 550and 560 generated as a result of the assimilation of transparent cachingserver logs 510 and 520 with the CDN caching server logs 530 and 540serve at least one of two purposes. Firstly, the CDN operator may usethe reports to provide comprehensive reporting for the content deliverythat is associated with content of each of the CDN's content providercustomers. In the prior art, it is typical for the CDN operator toprovide its content provider customers with performance metrics, networkusage metrics, distribution analysis, trends, histograms, etc. in orderfor the content provider customers to understand and appreciate thedemand for their content, who is consuming their content, where theircontent is being distributed to, as well as which content is in demand.However, such prior art reporting is deficient and incomplete in manyrespects because without assimilating transparent caching logs into thereporting, the reporting is based solely on the network usage that istracked to the logs of the CDN caching servers and does not account forthe network usage provided by the transparent caching servers that arelocated along the delivery path from the CDN to the end users.Consequently, this deficiency skews the metrics and numbers that arereported to the content provider customers, thereby providing thecontent provider customers a false and inaccurate representation of thereported performance metrics, network usage metrics, distributionanalysis, trends, histograms, etc. In the embodiments described herein,this reporting deficiency is resolved by the assimilation of thetransparent caching server logs with the CDN caching server logs.Specifically, by means of the assimilation, the CDN operator can nowprovide an end-to-end solution that accurately reports and accounts forall links in the delivery chain by which content is delivered from theCDN to end users. This deficiency, and how it is overcome by theend-to-end solution of the embodiments described herein, is presented inFIG. 6.

FIG. 6 illustrates the links in the delivery chain that contenttypically traverses when passing from a CDN to an end user. The firstlink in the delivery chain is the end user 610. The end user 610operates a network enabled device that requests and receives contentfrom a data network, such as the Internet. The network enabled devicecan include any computer, smartphone, tablet, personal hotspot, etc.Often, the second link in the delivery chain is at least one transparentcaching server 620 that is located in and operated by a Telco, whereinthe Telco provides the end user 610 with access to the data network. Inthis figure, the third link in the delivery chain is a CDN cachingserver 630. The fourth link in the displayed delivery chain is thecontent provider customer 640. The figure illustrates a log processingserver 635 of the CDN that performs log aggregation, log processing, andperformance reporting for the CDN. The figure also illustrates twoscenarios 650 and 660 for how content is served to the end user 610 inresponse to the end user 610 requesting the same content at differenttimes. It should be apparent to one of ordinary skill in the art thatthe delivery chain being presented in FIG. 6 omits, for purposes ofsimplicity, other non-caching links in the delivery chain, such astraffic management servers (e.g., DNS servers). Also, the delivery chainmay include multiple transparent caching servers and other cachingservers, but these servers have been omitted for purposes of simplicity.

In this figure, it is presumed that the content provider customer 640has exclusively contracted with the CDN to have the CDN deliver thecontent of the content provider customer 640 on behalf of the contentprovider customer 640. Accordingly, the content of the content providercustomer 640 is cached to the CDN caching server 630.

At 650, the end user 610 issues a first request for content of thecontent provider customer 640. The request passes through the Telcobefore passing to the external data network in which the CDN cachingserver 630 is located. When passing through the Telco, the transparentcaching server 620 analyzes the request from the end user 610 anddetermines whether the request should be intercepted based on whetherthe transparent caching server 620 has already cached the requestedcontent. At 650, the end user 610 request is the first request for thecontent of the content provider customer 640 that the transparentcaching server 620 receives. Therefore, the content is not cached at thetransparent caching server 620 and the request is permitted to passthrough the Telco to the external data network, where it is routed tothe CDN caching server 630. The CDN caching server 630 responds to therequest by serving the requested content to the end user 610 and the CDNcaching server 630 logs the network usage associated with serving thecontent. The content served from the CDN caching server 630 passes backthrough the Telco to reach the end user 610. In so doing, the contentpasses through the transparent caching server 620, which caches thecontent so that it may serve the content upon the next request for thatcontent.

At 660, the end user 610 again requests the content of the contentprovider customer 640. The transparent caching server 620 monitors therequest as it passes through the Telco and the transparent cachingserver 620 determines that it has the requested content cached, becausethis is now the second such request for the content. The transparentcaching server 620 intercepts the request. As a result, the request isnot routed to the CDN caching server 630 and the CDN operator has noknowledge that the content was requested a second time. The transparentcaching server 620 responds to the intercepted request by serving thecontent of the content provider customer 640 from cache and thetransparent caching server 620 logs the network usage associated withserving the content.

In the prior art in which the transparent caching server 620 is notassimilated with the CDN, the log processing server 635 generates areport solely based on logs of the CDN caching servers (CDN cachingserver 630). Such a report notifies the content provider customer 640that its content was requested once and the CDN details the networkusage associated with responding to that one request.

In the federated end-to-end CDN solution of some embodiments in whichthe transparent caching server 620 is assimilated with the cachingservers of the CDN, the log processing server 635 generates a reportbased on logs that are aggregated from the transparent caching server620 and the CDN caching server 630. Such a report notifies the contentprovider customer 640 that its content was requested twice and the CDNis able to detail the network usage associated with responding to bothrequests for the content provider customer's 640 content. Moreover, theend-to-end solution improves the performance metrics reported by the CDNbecause of the greater efficiency with which the transparent cachingserver 620 can respond to end user requests relative to the CDN cachingserver 630. Consequently, the metrics reported based on the end-to-endCDN solution will show improved performance relative to the solutionthat does not assimilate the transparent caching server performance withthe performance of the CDN caching servers. For example, assume that thedelay to serve content from the CDN caching server 630 to the end user610 is 20 milliseconds (ms) and assume that the delay to serve contentfrom the transparent caching server 620 to the end user 610 is 10 ms. Inthe prior art implementation in which the transparent caching server 620is not assimilated with the CDN, the average delay to serve the contentof the content provider customer 640 is 20 ms. However in the end-to-endsolution of some embodiments in which the transparent caching server 620is assimilated, the CDN can accurately and correctly report an averagedelay of 15 ms when the content of the content provider 640 wasrequested and served twice with the CDN caching server 630 responding tothe first request and the transparent caching server 620 responding tothe second request. The deficiency in the prior art implementationrelative to the federated end-to-end solution presented herein ismagnified when content is requested thousands of times and a significantpercentage (e.g., greater than 5%) of those requests are intercepted andresponded to by various transparent caching servers along the deliverychain.

This deficiency in reporting also presents the secondary purpose for theassimilation of transparent caching servers with the CDN cachingservers. This secondary purpose is to use the assimilated transparentcaching logs to allow the CDN operator to bill the content providercustomer for the end-to-end delivery of the content provider customer'scontent and the network usage associated with such delivery. Accordinglyand with reference back to FIG. 3, the process integrates (at 340) thepost-processed transparent caching server log for billing. Thisintegration involves combining the usage identified in thepost-processed log with usage that is identified from logs of thecaching servers of the CDN, to produce a comprehensive tally of thenetwork usage that is related to the delivery of content of a particularcontent provider customer of the CDN. The process then bills (at 350)the particular content provider customer for all such network usage.

This secondary purpose is illustrated with reference back to FIG. 6. Inthe prior art in which the transparent caching server 620 is notassimilated with the CDN, the log processing server 635 only accountsfor the network usage that is associated with serving the content fromthe CDN caching server 630 to the end user 610 when billing the contentprovider customer 640 for the network usage that is associated withdelivering the content provider customer's content 640. The logprocessing server 635 is unaware of the network usage that thetransparent caching server 620 consumes to serve the content providercustomer's content in response to the second request issued by the enduser 610. For instance in FIG. 6, it is presumed that one megabyte ofnetwork usage is consumed to the serve the content of the contentprovider customer 640. In the prior art scenario, the log processingserver 635 bills the content provider customer 640 for the one megabyteof network usage that the CDN caching server 630 consumed to serve thecontent at 650. However, the content provider customer is not chargedfor the additional one megabyte that is consumed by the transparentcaching server 620 to serve the content at 660. In the end-to-endsolution in which the transparent caching server 620 is assimilated withthe CDN, the log processing server 635 is aware of the second megabyteof network usage based on assimilation and processing of the transparentcaching server 620 log. The log processing server 635 can then bill thecontent provider customer 640 for two megabytes of network usage insteadof only one in the prior art scenario. The CDN is therefore compensatedfor all network usage that is related to the delivery of the contentprovider customer's content. As discussed above, the transparent cachingserver operator is also compensated, either by receiving fixedcompensation or variable compensation for providing the CDN access tothe transparent caching server log, wherein the fixed compensation is aonetime or recurring fee that is paid to the transparent caching serveroperator for each log access irrespective of the network usageidentified in the log, and wherein the variable compensation is a feethat is paid to the transparent caching server operator based on thenetwork usage that is identified in the accessed log and a percentage ofthe fee that the CDN operator collects from the content providercustomer for the identified network usage in the log.

To further monetize the network usage that is logged to the transparentcaching server log, the process may involve optionally redistributing(at 360) the aggregated transparent caching server logs to other CDNoperators. In some embodiments, redistributing the aggregatedtransparent caching server logs involves the CDN operator that has(exclusive or non-exclusive) access to the transparent caching serverlogs passing the logs to other CDN operators. The other CDN operatorsthen independently process the logs to identify network usage that isrelated to content of their own content provider customers. These otherCDN operators can then bill their content provider customers for theidentified network usage. In return, the other CDN operators pay the CDNoperator that redistributes the transparent caching server logs a feefor such access. In some embodiments, redistributing the aggregatedtransparent caching server logs involves the CDN operator that has(exclusive or non-exclusive) access to the transparent caching serverlogs processing the logs on behalf of other CDN operators. In thismanner of redistributing the logs, the actual logs remain in thepossession of a single CDN operator. That single CDN operator thenidentifies network usage that is related to content provider customersof other CDN operators and reports such network usage to the other CDNoperators. To do so, the other CDN operators provide a list ofidentifiers (i.e., an association table) that identify their contentprovider customers to the CDN operator that has access to thetransparent caching server logs, so that the CDN operator can performthe processing of the logs on behalf of the other CDN operators. Theother CDN operators can then compensate the CDN operator for performingthe processing. For these reasons, it is envisioned that exclusivity inthe bilateral agreements established with the transparent caching serveroperators is valuable to the CDN operator.

FIG. 7 illustrates how a first CDN operator can further monetize atransparent caching server log by redistributing the transparent cachingserver log to second and third CDN operators in accordance with someembodiments. The figure depicts a transparent caching server operator710 that operates a transparent caching server 715, a transparentcaching server log 720 with entries 730, 735, 740, 745, and 750, a firstCDN operator 760 with content provider customer 765, a second CDNoperator 770 with content provider customer 775, and a third CDNoperator 780 with content provider customer 785.

The first CDN operator 760 enters into a bilateral agreement with thetransparent caching server operator 710. For the purposes of FIG. 7, itis assumed that the bilateral agreement contains an exclusivity clausethat provides the first CDN operator 760 exclusive access to the log 720of the transparent caching server 715 while preventing the second CDNoperator 770 and the third CDN operator 780 from obtaining access to thelog 720 from the transparent caching server 715 of the transparentcaching server operator 710.

The first CDN operator 760 aggregates the log 720 from the transparentcaching server 715. The first CDN operator 760 processes the log 720 inaccordance with the above described processes and identifies thatentries 735 and 750 track network usage that is related to deliveringcontent for the content provider customer 765 of the first CDN operator760. The first CDN operator 760 bills the content provider customer 765for such network usage and collects payment from the content providercustomer 765. The first CDN operator 760 may bill the content providercustomer 765 solely for the network usage that is identified in the log720 or may bill the content provider customer 765 for the network usagethat is identified in the log 720 and the network usage that isidentified in the logs that are aggregated from the caching servers thatare operated by the first CDN operator 760.

The first CDN operator 760 compensates the transparent caching serveroperator 715 for granting exclusive access to the log 720. Thecompensation may include a fixed fee or may be dependent on the paymentthat the first CDN operator 760 collects from the content providercustomer 765 for the network usage that is identified in the log 720.

The first CDN operator 760 then distributes the log 720 to the secondCDN operator 770. The second CDN operator 770 processes the log 720 inaccordance with the above-described processes. As part of theprocessing, the second CDN operator 770 identifies that entry 740 in thelog 720 tracks network usage that is related to delivering content forthe content provider customer 775 of the second CDN operator 770. Thesecond CDN operator 770 incorporates the network usage associated withentry 740 into its performance and statistics reports, wherein thereports can be viewed by the content provider customer 775 to determinedemand, various performance metrics, and overall network usage fordelivery of the content provider customer's 775 content. Additionally,the second CDN operator 770 uses the identified network usage to billthe content provider customer 775 for the network usage in entry 740 andcollects payment from the content provider customer 775. The second CDNoperator 770 compensates the first CDN operator 760 for the access tothe log 720. The compensation can be a fixed compensation or a variablecompensation. A separate bilateral agreement between the first CDNoperator 760 and the second CDN operator 770 may set forth the terms andconditions with which the first CDN operator 760 provides the second CDNoperator 770 access to the log 720. As part of this agreement, the formand amount of compensation are detailed. Also as part of the agreement,the first CDN operator 760 can prevent the second CDN operator 770 fromredistributing the log 720 to any other entity.

The first CDN operator 760 then distributes the log 720 to the third CDNoperator 780. The third CDN operator 780 processes the log 720 inaccordance with the above-described processes. The third CDN operator780 identifies that no entries track network usage that is related todelivering content for the content provider customer 785 of the thirdCDN operator 780. The third CDN operator 780 is thus unable to bill thecontent provider customer 785 for any network usage in the log 720, butmay nevertheless be obligated to pay the first CDN operator 760 a feefor being provided access to the log 720.

In the manner of transparent caching server log redistribution presentedin FIG. 7, each CDN operator is able to maintain autonomy and privacywhile still obtaining access to the transparent caching server log 720.Specifically, CDN operators can keep content provider customer lists andcontent provider customer identifiers internal and not expose them toother CDN operators. By redistributing the log to different CDNoperators, each receiving CDN operator can independently process the log720 to identify the network usage for its content provider customers.Unidentified network usage will be of no value to the CDN operator.

As noted above and in accordance with some embodiments, the first CDNoperator with exclusive access to the log 720 can redistribute thenetwork usage in the log 720 without providing other CDN operatorsaccess to the log 720. This is accomplished by entering into a bilateralagreement with a second CDN operator, whereby the second CDN operatoragrees to provide the first CDN operator an association table withvarious identifiers for content provider customers of the second CDNoperator. The first CDN operator then processes the log to identifynetwork usage that relates to its own content provider customers whilealso identifying network usage that relates to content providercustomers of the second CDN operator. The first CDN operator then passesthe identified network usage for the content provider customers of thesecond CDN operator to the second CDN operator. The second CDN operatorcan incorporate the identified network usage into its reports and canuse the identified network usage to bill the corresponding contentprovider customers for the network usage. In this manner, the second CDNoperator is never provided access to the transparent caching serverlogs, but is still able to benefit from the logs by having the first CDNoperator identify the network usage for content provider customers ofthe second CDN operator on behalf of the second CDN operator.

The foregoing sets forth an end-to-end CDN solution that requires nochange to the existing operation of the transparent caching servers orthe CDN caching servers when assimilating the transparent caching serverlogs in the reporting and billing functionality of the CDN. Suchembodiments may be preferred when the transparent caching servers beingassimilated are from different manufacturers. More specifically, theoperation of the transparent caching servers from the differentmanufactures is likely to not be not standardized and therefore,specific functionality that may otherwise be needed to facilitate theirassimilation into the CDN may be absent from one or more of thetransparent caching servers.

However, various advantages can be realized when the transparent cachingservers are enhanced such that their operation provides functionality insupport of the end-to-end CDN solution. These enhancements, whenimplemented, can reduce the processing overhead of the log processingserver in determining which entries of the aggregated transparentcaching server logs track network usage for content provider customersof the CDN operator. These enhancements can also enable more intelligentcaching at the transparent caching servers such that caching of CDNcustomer content is prioritized over other content. In so doing, thedelivery of the CDN customer content is better accelerated and thetransparent caching server operator better monetizes on the content thatis delivered by the transparent caching servers under its control.

In some embodiments, the enhancements include (1) the introduction ofCDN keys in packets disseminated by the CDN caching servers, (2) thelogging of the CDN keys by the transparent caching servers, and (3) theprocessing of the CDN keys by the log processing server as part of thereporting and billing function of the CDN. The CDN keys are encoded orhashed values that uniquely identify the content provider customers of aCDN or, more granularly, different content of the different contentprovider customers of a CDN. The CDN keys are embedded in the headerfields of the transmitted packets.

The CDN keys for the different content provider customers of a CDN canbe generated by the CDN caching servers or by a central server such asthe log processing server of the CDN using one or more hashingfunctions. The hashing functions accept a name or other identifier(e.g., URL, domain name, etc.) of the CDN content provider customer asinput, hash the input, and produce a unique integer value as output thatserves as the CDN key. To identify specific content of a CDN contentprovider customer as a unique integer value, the hashing functionsaccept a name or other identifier of the CDN content provider customerand name or other identifier of the content as input, hash the input,and produce a unique integer value that represents content of the CDNcustomer. When using the CDN keys, the association table can besimplified to provide a mapping between the CDN keys and the customersor customer content that they represent.

The CDN keys are introduced within the header fields of the contentdisseminated from the CDN caching servers through the transparentcaching servers en route to the end users requesting the content.Preferably, the CDN keys are embedded within the layer 7 or applicationlayer header of the packets encapsulating the content. For instance, aCDN key for a specific CDN content provider customer can be introducedwithin the HTTP header of the packet encapsulating the content of thatspecific CDN content provider customer. The CDN keys may be introducedin an optional header field, as a non-standard header field, within arequired but unused header field, or as part of a parameter of arequired header field.

As a result of introducing the CDN keys, a transparent caching serverthat is enhanced to identify the new CDN keys can readily distinguishCDN customer content from other content. For instance, when a CDNcaching server serves the same content as another server through atransparent caching server, the transparent caching server can readilydistinguish the content served by the CDN caching server from thecontent served by the other server based on the presence of the CDN key.The enhancement to the transparent caching server enables thetransparent caching server to more intelligently manage its cache.Specifically, the transparent caching server can prioritize the cachingof the CDN customer content over other content and prevent or delay theremoval of CDN customer content from cache. This results in betteraccelerated delivery of the CDN customer content. This also results inthe transparent caching server serving more CDN customer content and inturn, results in better monetization as the CDN compensates thetransparent caching server operator for the delivery of CDN customercontent and no compensation is otherwise provided for the delivery ofother content.

FIG. 8 presents a process 800 that is performed by an enhancedtransparent caching server to utilize the CDN keys in support of theend-to-end CDN solution. The process commences when the enhancedtransparent caching server receives (at 810) an end user request forcontent that is not cached at the enhanced transparent caching server.As with non-enhanced operation, the process does not intercept therequest and allows the request to pass (at 820) upstream to the externaldata network. In some embodiments, the process involves intercepting therequest and reissuing the request such that it appears to haveoriginated from the enhanced transparent caching server. The processthen receives and monitors (at 830) the downstream content that isserved from the external data network in reply to the request.Specifically, the monitoring determines (at 835) whether the downstreamcontent includes a CDN key by analyzing the headers of the downstreamcontent.

When the content does not include a CDN key, the process invokes (at840) a first caching policy. The first caching policy controls whetherthe transparent caching server caches the content before passing itthrough to the requesting end user or whether the transparent cachingserver passes the content through without caching.

When the content includes a CDN key, the process invokes (at 845) asecond caching policy. Like the first caching policy, the second cachingpolicy controls whether the transparent caching server caches thecontent before passing it through to the requesting end user or whetherthe transparent caching server passes it through without caching.However, the second caching policy is provided priority over the firstcaching policy. This ensures that the cache of the transparent cachingserver is primarily allocated to caching content that is associated witha CDN key (i.e., CDN customer content) and secondarily allocated tocaching other content. Should the cache be full, the caching policieswill cause CDN customer content to be retained while other content isreplaced (unless the cached CDN customer content has become stale). Inmany instances, the second caching policy will be a first hit cachingpolicy. Also, the second caching policy can be implemented as a granularcaching policy, whereby different degrees of priority are provided basedon the CDN content provider customer or content that is identified bythe CDN key. In this manner, content of some CDN customers can be givenpriority over content of other CDN customers. For example, it may bethat a specific CDN customer is providing a live stream of a highlypopular event. Therefore, the second caching policy may be modified sothat the CDN key identifying the popular content is stored to cache uponthe first request and retained in cache for a specified duration whileother CDN customer content is cached upon the second request andreplaced from cache when the cache becomes full.

Next, the process determines (at 850), based on the invoked cachingpolicy, whether the content should be cached before passing to therequested end user. If not, the process optionally extracts (at 860) theCDN key from the content when the content includes the CDN key, theprocess passes (at 870) the content to the requesting end user, and theprocess ends. The extracting of the CDN key prevents the requesting enduser (that receives the content) from having any knowledge of the CDNkey. In some embodiments, the extraction of the CDN key is not performedas it will likely be ignored by the end user receiving the content. Ifthe process determines (at 850) that the content should be cached, thenthe process caches (at 855) the content and stores the variousidentifiers including the CDN key when it is present. The process thenoptionally performs (at 860) the CDN key extraction before passing (at870) the content to the requesting end user and then the process ends.

Subsequently, when a request for cached content is received at theenhanced transparent caching server, the server will intercept therequest and serve the requested content out of cache. The transparentcaching server will log the data network usage that is associated withserving the requested content. Additionally, the transparent cachingserver will include a CDN key with the logged data network usage if theCDN key was associated with the served cached content or if the contentbeing served is CDN customer content. Including the CDN key in thetransparent caching serve log simplifies log processing at the logprocessing server, because the log processing server can readilyidentify transparent cache server log entries that relate to thedelivery of CDN customer content from other content by identifyingentries that include a CDN key. Additionally, inclusion of the CDN keyavoids any confusion as to whether a CDN customer is to be charged forthe content delivery provided by the transparent caching server whenthat CDN customer has other servers besides the CDN caching serversserving some or all of the CDN customer's content.

During log processing, the log processing server aggregates the logsfrom the enhanced transparent caching servers. The log processing serverintegrates the data network usage from the transparent caching serverlogs with the data network usage of the CDN caching server logs bymatching log entries that have the same CDN key. The log processingserver can then perform a reverse hash or perform a lookup into theassociation table to determine which one or more CDN keys representwhich one or more CDN content provider customers in order to report andbill for the total network data usage by each such CDN customer.

Further enhancements can be made to the operation of the transparentcaching servers to seamlessly assimilate the transparent caching serversas extended PoPs of the CDN. These enhancements resolve issues withrespect to how to attribute performance metrics derived from contentserved by the transparent caching servers to the transparent cachingservers instead of intermixing those metrics with those derived from thecontent served by the CDN caching servers.

FIG. 9 illustrates assimilating a transparent caching server as anextended PoP of the CDN in accordance with some embodiments. This figureincludes an end user 910, the transparent caching server 920, and a CDNcaching server 930. For exemplary purposes, the transparent cachingserver 920 is assigned IP address 1.1.1.1 and the CDN caching server 930is assigned IP address 2.2.2.2.

As shown, the transparent caching server 920 intercepts a request thatis intended for the CDN caching server 930. The transparent cachingserver 920 has the requested content cached. Therefore, rather than passthe request to the CDN caching server 930, the transparent cachingserver 920 serves the requested content from cache. The end user 910 isunaware that the content is served by the transparent caching server 920and not the CDN caching server 930, because the transparent cachingserver emulates the CDN caching server 930 by inserting the IP addressof the CDN caching server 930 in the source IP address field of thepackets that are sent from the transparent caching server 920 to the enduser 910.

When logging the data network usage that is associated with thedelivered content, the transparent caching server 920 would normallypopulate the log using the same parameters as those used to deliver thecontent. Specifically, the source IP address would be that of the CDNcaching server 930. However, during log processing, the emulated IPaddress would lead to improperly attributing the content delivery andany derived performance metrics to the CDN caching server 930 and notthe transparent caching server 920. Accordingly, to seamlesslyassimilate the transparent caching server 920 as an extended PoP of theCDN, the operation of the transparent caching server 920 is enhanced sothat when the transparent caching server 920 logs data network usage, itinserts its own IP address as the source IP address instead of theemulated IP address. The transparent caching server 920 may also inserta CDN key as part of the log entry if one is associated with the contentthat was served. As a result, when the log processing server aggregatesa log from the transparent caching server 920, the log processing servercan generate reports for the CDN content provider customers thatillustrate the transparent caching server 920 as an extended PoP andthat present data network usage and performance metrics for the extendedPoP.

In some embodiments, transparent caching servers can be assimilated asextended PoPs of the CDN without enhancing the operation of thetransparent caching servers. In some such embodiments, the logprocessing server tags each log that it aggregates from a transparentcaching server with the IP address of the transparent caching server.Prior to log processing, the source IP address fields within theaggregated transparent caching server log are replaced with the taggedIP address of the transparent caching server. Once replaced, the logprocessing server can correctly attribute network usage and performancemetrics to the extended PoP represented by the transparent cachingserver rather than the PoP of a CDN caching server or other originserver that is emulated by the transparent caching server.

Thusfar, the end-to-end solution has been described relative to animplementation model that involves a CDN operator and a transparentcaching server operator. However, some embodiments of the end-to-end CDNsolution may be implemented by an alternative model that involves a CDNoperator, a broker, and one or more transparent caching serveroperators.

In some embodiments, transparent caching server operators enter into abilateral agreement with the broker instead of a CDN operator. Thebroker secures (exclusive or non-exclusive) access to transparentcaching server logs of one or more transparent caching server operators.The broker then acts as a reseller that sells access to the transparentcaching server logs on behalf of the transparent caching serveroperators. Such a scenario may be preferred when a transparent cachingserver operator is small in scope. Specifically, when a transparentcaching server operator operates only one or a few transparent cachingservers, the transparent caching server operator will have little valueto offer a CDN operator. In other words, one or a few transparentcaching server logs may not provide the CDN operator enough value tocompensate the transparent caching server operator for access to thosefew logs. However, a broker can first enter into bilateral agreementswith several transparent caching server operators. When the broker hasaccess to a large bundle of transparent caching server logs (e.g., morethan fifty), the broker can negotiate terms with one or more CDNoperators to sell access to the entire bundle of transparent cachingserver logs.

FIG. 10 presents a process 1000 performed by a broker acting as areseller of transparent caching server logs in accordance with someembodiments. The process 1000 commences with the broker entering (at1010) into a first set of (exclusive or non-exclusive) bilateralagreements with one or more transparent caching server operators thatcollectively operate a large number of transparent caching servers. Forinstance, the broker may enter into a first bilateral agreement with afirst transparent caching server operator that operates two transparentcaching servers and a second bilateral agreement with a secondtransparent caching server operator that operates fifteen transparentcaching servers. As part of the bilateral agreements entered into at1010, the broker agrees to compensate each transparent caching serveroperator that is a party to a bilateral agreement with the broker somemonetary fee in return for providing the broker access to the logs ofthe transparent caching servers that are under the control of theoperator. The compensation may vary per transparent caching serveroperator based on the overall contribution to the entire bundle oftransparent caching server logs by a particular operator.

The process continues with the broker entering (at 1020) into a secondset of bilateral agreements with one or more CDN operators. As part ofthe second set of bilateral agreements entered into at 1020, the brokeragrees to provide the CDN operators that are parties to the second setof bilateral agreements access to the full set or substantial set oftransparent caching server logs that the broker has obtained access toas a result of the first set of bilateral agreements. In return, the CDNoperators agree to compensate the broker for such access.

The process aggregates (at 1030) the transparent caching server logsfrom the transparent caching servers of each operator that is a party tothe first set of bilateral agreements. The broker may optionally formatthe aggregated logs to produce a unified format for the logs. Also, thebroker may optionally combine the entries from each of the aggregatedlogs into a single log. The process then distributes (at 1040) theaggregated transparent caching server logs to the CDN operators that areparties to the second set of bilateral agreements. The CDN operators canprocess the logs to identify network usage for their content providercustomers. The process receives (at 1050) compensation from the CDNoperators for access to the aggregated set of transparent caching serverlogs. The process distributes (at 1060) some or all of the receivedcompensation amongst the transparent caching server operators. Thecompensation may be distributed based on each transparent cachingserver's contribution to the bundle of aggregated logs. For example, anoperator that provides access to ten transparent caching server logs maybe compensated ten times as much as an operator that provides access toa single transparent caching server log. In some embodiments, thecompensation is more granular. For example, the transparent cachingserver operators are compensated based on the number of total entriesfrom the logs aggregated from servers of the operators. Consequently,operators of transparent caching servers that serve large amounts ofcontent that the CDNs are contracted to serve are compensated greaterthan operators of transparent caching servers that serve other contentthat the CDNs are not contracted to server.

In some embodiments, the broker does not distribute the aggregated logsto the CDN operators. Instead as part of the second set of bilateralagreements, the CDN operators provide identifiers (i.e., associationtables) for their content provider customers to the broker. The brokerthen processes the aggregated logs on behalf of the CDN operators. Thenetwork usage that is identified for content provider customers of aparticular CDN operator as a result of the processing is then passed tothat particular CDN operator in return for some amount of compensation.In this manner, the broker can charge the CDN operators a variable feefor the network usage that is identified in the aggregate set of logs,while also compensating each transparent caching server operator avariable fee for the total amount of network usage that is related todelivering content for content provider customers of various CDNoperators.

The end-to-end CDN solution described thus far promotes a federated CDNin which one CDN operator is able to leverage resources of third partiesin order to improve its content delivery capabilities. The precedingdescription and figures describe a federated CDN wherein the thirdparties participating in the federation include transparent cachingserver operators. In some embodiments, the participants to thefederation may additionally include other CDN operators, such that afirst CDN operator can use resources of a second CDN operator and atransparent caching server operator to perform improved contentdelivery.

FIG. 11 illustrates a fully federated CDN, wherein a first CDN operatorassimilates resources of a transparent caching server operator andresources of a second CDN operator in accordance with some embodiments.The first CDN operator 1110 independently operates a set of cachingservers 1120, traffic management server 1125, and a log processingserver 1127. The transparent caching server operator 1130 independentlyoperates transparent caching server 1135. The second CDN operator 1140independently operates a set of caching servers 1150, traffic managementserver 1155, and a log processing server 1160.

As part of the federation, the first CDN operator 1110 is permitted toleverage the content delivery capabilities of the transparent cachingserver 1135 and the set of caching servers 1150 of the second CDNoperator 1140 in order to deliver content for content provider customersof the first CDN operator 1110. To do so, a first bilateral agreement isestablished between the first CDN operator 1110 and the transparentcaching server operator 1130 in the manner described above and a secondbilateral agreement is established between the first CDN operator 1110and the second CDN operator 1140. The second bilateral agreement is onethat permits the first CDN operator 1110 to place content for one ormore of its content provider customers on one or more of the set ofservers 1150 that is operated by the second CDN operator 1140, so thatsuch content is served from the set of servers 1150 in addition to orinstead of being served from the set of servers 1120. Specifically, thefirst CDN operator 1110 purchases unused bandwidth from the second CDNoperator 1140 for its own usage. The second CDN operator 1140 thenreports network usage and other performance metrics back to the firstCDN operator 1110, so that the first CDN operator 1110 can bill itscontent provider customers accordingly. Further description forfederating two or more CDNs is provided in the United States provisionalpatent application with Ser. No. 61/524,294 entitled “Open ContentDelivery Network Platform with Capacity Exchange”.

As shown, the log processing server 1127 of the first CDN operator 1110aggregates logs from the set of caching servers 1120 that is operated bythe first CDN operator 1110, the transparent caching server 1135, andthe set of caching servers 1150 that is operated by the second CDNoperator 1140. In some embodiments, the log processing server 1127aggregates the logs of the set of caching servers 1150 from the logprocessing server 1160 of the second CDN operator 1140.

The log processing server 1127 processes the aggregated logs to identifytotal network usage by a content provider customer of the first CDNoperator 1110. In this federated CDN, the total network usage canaccount for content of the content provider customer that is deliveredby the one or more of the set of caching servers 1120, the transparentcaching server 1135, and the set of servers 1150. The first CDN operator1110 compensates each of the transparent caching server operator 1130and the second CDN operator 1140 for providing access to the logs.

III. Server System

Many of the above-described processes and components are implemented assoftware processes that are specified as a set of instructions recordedon non-transitory computer readable storage medium (also referred to ascomputer readable medium). When these instructions are executed by oneor more computational element(s) (such as processors or othercomputational elements like ASICs and FPGAs), they cause thecomputational element(s) to perform the actions indicated in theinstructions. Server, computer, and computing machine are meant in theirbroadest sense and may include any electronic device with a processorthat executes instructions stored on computer readable media or that areobtained remotely over a network connection. Examples of computerreadable media include, but are not limited to, CD-ROMs, flash drives,RAM chips, hard drives, EPROMs, etc. Further, wherever a server isidentified as a component of the embodied invention, it is understoodthat the server may be a single physical machine, or a cluster ofmultiple physical machines performing related functions, or virtualizedservers co-resident on a single physical machine, or variouscombinations of the above.

FIG. 12 illustrates a computer system or server with which someembodiments are implemented. Such a computer system includes varioustypes of computer readable mediums and interfaces for various othertypes of computer-readable mediums that implement the processes for theend-to-end CDN solution described above (e.g., the transparent cachingserver, CDN caching server, and log processing server). Computer system1200 includes a bus 1205, a processor 1210, a system memory 1215, aread-only memory 1220, a permanent storage device 1225, input devices1230, and output devices 1235.

The bus 1205 collectively represents all system, peripheral, and chipsetbuses that communicatively connect the numerous internal devices of thecomputer system 1200. For instance, the bus 1205 communicativelyconnects the processor 1210 with the read-only memory 1220, the systemmemory 1215, and the permanent storage device 1225. From these variousmemory units, the processor 1210 retrieves instructions to execute anddata to process in order to execute the processes of the invention. Theprocessor 1210 is a processing device such as a central processing unit,integrated circuit, graphical processing unit, etc.

The read-only-memory (ROM) 1220 stores static data and instructions thatare needed by the processor 1210 and other modules of the computersystem. The permanent storage device 1225, on the other hand, is aread-and-write memory device. This device is a non-volatile memory unitthat stores instructions and data even when the computer system 1200 isoff. Some embodiments of the invention use a mass-storage device (suchas a magnetic or optical disk and its corresponding disk drive) as thepermanent storage device 1225.

Other embodiments use a removable storage device (such as a flash drive)as the permanent storage device Like the permanent storage device 1225,the system memory 1215 is a read-and-write memory device. However,unlike the storage device 1225, the system memory is a volatileread-and-write memory, such as random access memory (RAM). The systemmemory stores some of the instructions and data that the processor needsat runtime. In some embodiments, the processes are stored in the systemmemory 1215, the permanent storage device 1225, and/or the read-onlymemory 1220.

The bus 1205 also connects to the input and output devices 1230 and1235. The input devices enable the user to communicate information andselect commands to the computer system. The input devices 1230 include,but are not limited to, alphanumeric keypads (including physicalkeyboards and touchscreen keyboards) and pointing devices (also called“cursor control devices”). The input devices 1230 also include audioinput devices (e.g., microphones, MIDI musical instruments, etc.). Theoutput devices 1235 display images generated by the computer system. Theoutput devices include, but are not limited to, printers and displaydevices, such as cathode ray tubes (CRT) or liquid crystal displays(LCD).

Finally, as shown in FIG. 12, bus 1205 also couples computer 1200 to anetwork 1265 through a network adapter (not shown). In this manner, thecomputer can be a part of a network of computers (such as a local areanetwork (“LAN”), a wide area network (“WAN”), or an Intranet, or anetwork of networks, such as the Internet.

As mentioned above, the computer system 1200 may include one or more ofa variety of different computer-readable media. Some examples of suchcomputer-readable media include RAM, ROM, read-only compact discs(CD-ROM), recordable compact discs (CD-R), rewritable compact discs(CD-RW), read-only digital versatile discs (e.g., DVD-ROM, dual-layerDVD-ROM), a variety of recordable/rewritable DVDs (e.g., DVD-RAM,DVD-RW, DVD+RW, etc.), flash memory (e.g., SD cards, mini-SD cards,micro-SD cards, etc.), magnetic and/or solid state hard drives, ZIP®disks, read-only and recordable blu-ray discs, any other optical ormagnetic media, and floppy disks.

While the invention has been described with reference to numerousspecific details, one of ordinary skill in the art will recognize thatthe invention can be embodied in other specific forms without departingfrom the spirit of the invention. Thus, one of ordinary skill in the artwould understand that the invention is not to be limited by theforegoing illustrative details, but rather is to be defined by theappended claims.

1. A method for assimilating operation of a transparent caching serverwith a content delivery network (CDN) operating of a set of CDN cachingservers, wherein the transparent caching server is not operated by theCDN, the method comprising: configuring the transparent caching serverto inspect content passing to the transparent caching server en route toan end user for presence of a CDN key, wherein the CDN key identifiescontent that the CDN serves on behalf of a CDN customer; caching firstcontent passing to the transparent caching server according to a firstcaching policy when the first content does not include a CDN key;logging data network usage associated with serving the first contentfrom cache, wherein the logging comprises tracking the data networkusage associated with the serving of the first content to a first set ofentries of a log of the transparent caching server without associating aCDN key to the first set of entries, wherein not associating a CDN keyto the first set of entries identifies that the first set of entriesdoes not identify data network usage for content of a CDN customer thatis served by the transparent caching server; caching second contentpassing to the transparent caching server according to a second cachingpolicy when the second content includes a CDN key, wherein the secondcaching policy is provided precedence over the first caching policy incontrolling content that is cached at the transparent caching server;and logging data network usage associated with serving the secondcontent from cache, wherein the logging comprises tracking the datanetwork usage associated with the serving of the second content to asecond set of entries of the log with an associated CDN key to identifythat the second set of entries identify data network usage for contentof a CDN customer that is served by the transparent caching server. 2.The method of claim 1 further comprising providing the data networkusage logged to the second set of entries to the CDN.
 3. The method ofclaim 1 further comprising inspecting headers of packets encapsulatingthe first content and the second content for presence of a CDN key. 4.The method of claim 1, wherein a CDN key is a hashed value identifying aparticular customer of the CDN.
 5. The method of claim 1, whereincaching the second content according to the second caching policycomprises removing the first content from cache when the cache is full.6. The method of claim 5, wherein caching the first content according tothe first caching policy comprises retaining the second content in cacheand not caching the first content when the cache is full.
 7. The methodof claim 1 further comprising configuring the transparent caching serverwith an IP address.
 8. The method of claim 7, wherein logging the datanetwork usage comprises providing the IP address of the transparentcaching as the source IP address for at least each log entry of thesecond set of entries.
 9. The method of claim 1 further comprisingextracting the CDN key from the second content when serving the secondcontent.
 10. A method for assimilating operation of a transparentcaching server with a content delivery network (CDN) operating of a setof CDN caching servers, wherein the transparent caching server is notoperated by the CDN, the method comprising: aggregating a first log filefrom the transparent caching server, the first log file tracking datanetwork usage for content served by the transparent caching server;aggregating at least a second log file from at least one CDN cachingserver of the set of CDN caching servers, the second log file trackingdata network usage for content served by the at least one CDN cachingserver; identifying data network usage from the first log file forcontent of a particular CDN customer that was served by the transparentcaching server; identifying data network usage from the second log filefor content of the particular CDN customer that was served by the atleast one CDN caching server; presenting the data network usage that isidentified from the first log file as content of the particular CDNcustomer that is delivered from a first Point-of-Presence (PoP) of theCDN; presenting a holistic report for content of the particular CDNcustomer that is delivered by the CDN by grouping the identified datanetwork usage from the first log file with at least the identified datanetwork usage from the second log file.
 11. The method of claim 10further comprising presenting the data network usage that is identifiedfrom the second log file as content of the particular CDN customer thatis delivered from at least a second PoP of the CDN.
 12. The method ofclaim 10 further comprising billing the particular CDN customer for theidentified data network usage from at least the first log file and thesecond log file.
 13. The method of claim 10 further comprisingdetermining an amount of compensation to provide to an operator of thetransparent caching server based on the identified data network usagefrom the first log file.
 14. The method of claim 10 further comprisinggenerating a unique CDN key for each CDN customer of a plurality of CDNcustomers.
 15. The method of claim 14 further comprising passing a CDNkey identifying the particular CDN customer with content of theparticular CDN customer.
 16. The method of claim 14, wherein identifyingthe data network usage from the first log file for content of theparticular CDN customer comprises extracting entries in the first logfile that include a CDN key for the particular CDN customer.
 17. Amethod for assimilating operation of a transparent caching server with acontent delivery network (CDN) operating of a set of CDN cachingservers, wherein the transparent caching server is not operated by theCDN, the method comprising: configuring a first address identifier toidentify the transparent caching server; intercepting a request forcontent that is intended for a server identified by a second addressidentifier, wherein the second address identifier is different than thefirst address identifier; serving the requested content from thetransparent caching server using the second address identifier foridentifying a source of the content; tracking data network usage forserving the requested content to a log by entering in the log the firstaddress identifier in place of the second address identifier for thesource of the content; and providing the log to the CDN for assimilationof the data network usage tracked by the transparent caching server withdata network usage that is tracked by the set of CDN caching servers.18. The method of claim 17 further comprising receiving compensationfrom the CDN based on the data network usage that is tracked to the log.19. The method of claim 17 further comprising establishing an agreementwith the CDN to provide the CDN access to the log of the transparentcaching server in return for compensation by the CDN.
 20. The method ofclaim 17, wherein tracking the data network usage comprises associatingan identifier with the data network usage that is tracked to the log,said identifier for distinguishing data network usage for servingcontent of a customer of the CDN from data network usage for servingcontent not belonging to a customer of the CDN.
 21. The method of claim17, wherein tracking the data network usage comprises associating a keywith the data network usage for content of a customer of the CDN andomitting a key when tracking the data network usage that is unrelated tocontent of a customer of the CDN.